5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
- Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-3: Data Dictionary

Work Fields


You can define temporary domain-type fields called work fields to calculate, temporarily store, or display values that are not stored in a file. A work field is analogous to a record that has no file storage characteristics and contains a single field. A work field has no sequence number and no relationship to any files, records, or other work fields. You can manipulate work fields in much the same fashion as any other field.

You cannot save a value in a work field after a user exits APPX. To save a work field value, you must copy it into a field that is part of a permanent file's record. You cannot define a group of work fields because they are not arranged in a predictable order. Work fields cannot be keys because they are not part of a record structure within a file.

When adding work fields to the data dictionary Appx will start the work field name with the word WORK by default. This is similar to naming fields begining with the file name. This helps to identify the field as a work field throughout your application. You can overwrite the word WORK if you so prefer.

Application Design Manual                                         "Powered by Appx Software"

42

©2006 By APPX Software, Inc. All Rights Reserved